Zendesk digest: link unflagged tickets, list new non-English ones; sogs-ban: show posted names - #76

A ticket the model did not mark worth looking into was only counted in the
header's category tally, then recorded as reported, so it never reached
Discord as a link at all. #28891, a lost recovery phrase, went that way.

They now get one line under the abuse reports, grouped by category, most
common first, with the same link budget and a count that covers them all.

Claude-Session: https://claude.ai/code/session_019cnvrsCXsqLykDyQburD2f

The digest translated only the tickets it gave a card, a scope set for the
Comment button those cards no longer carry. 2 of the 35 non-English tickets
in the queue had a transcript.

Every ticket the run classifies is now passed to attach_english. Unchanged
tickets are skipped before classification, so each one is translated once
per change in its conversation.

Claude-Session: https://claude.ai/code/session_019cnvrsCXsqLykDyQburD2f

The digest wrote its English rendering into a ticket field that nothing
reads any more. It now posts the private note `claude: english` writes,
with the same marker, so whichever gets there first stops the other
repeating it until the customer writes again.

translate_conversation and english_note are shared by both. The field
code, its env setting and its tests are gone.

Claude-Session: https://claude.ai/code/session_019cnvrsCXsqLykDyQburD2f

… feat/digest-translate-every-ticket

…eat/digest-translate-every-ticket

A long conversation was cut to 8000 characters from its end, dropping the customer's
newest message mid-JSON, and the turns cut off counted as already English: a long
English ticket got a transcript on every message, and a long foreign one a note whose
marker covered a turn it never translated. Whole turns now go from the oldest end, the
newest is clipped only when it alone is too long, and the note says how many were left
out.

The relay runs one note_reply at a time per ticket and waits 60 seconds after a
customer message, restarted by each further one, so a burst of messages costs one
translation and two runs cannot both post it. note_reply also re-reads the ticket for
the marker just before writing.

…translating them

The relay no longer translates when the customer writes: no customer event, no
debounce, no --english-if-needed. The digest instead leads its entries with a 🌐 line
linking every ticket reported for the first time that is not in English, with its
language, for an agent to answer `claude: english` on.

`claude: english` keeps the newest turns whole, drops the oldest when the
conversation is too long and says how many, and checks for the transcript again
just before writing it.

…ding a stale draft

Once support has replied on a ticket, `claude: draft` gives Claude the conversation
so far and the customer's newest message separately, and asks it to answer only the
newest one without repeating earlier replies. A draft with a public comment after it
is no longer amended, since it was already sent or overtaken.

`claude: reply` no longer sends a draft the customer has written after. It says so
and waits for `claude: reply [n] anyway`.

Only a reply this tool sent, or the customer writing, makes the next draft start fresh.